Skip to content

Make auto-label.yml runnable: pin issue-labeler, add permissions - #21

Merged
Pnwcomputers merged 1 commit into
mainfrom
fix/auto-label-workflow
Nov 17, 2026
Merged

Pnwcomputers merged 1 commit into
mainfrom
fix/auto-label-workflow

Conversation

@Pnwcomputers

Copy link
Copy Markdown
Owner

Follow-up to #20. That PR moved the issue-labeler config to .github/labeler.yml. This commit was meant to be part of it, but it was pushed after #20 had already merged, so it never reached main.

Problem

auto-label.yml has never worked. Its only run (Apr 2026) failed during job setup, with no steps run. There are three problems:

Problem Fix
github/issue-labeler@v3 doesn't resolve: upstream has only v3.0–v3.5 tags, with no floating v3 pin @v3.5 (latest, Aug 2026)
enable-versioned-regex is a required input and wasn't set enable-versioned-regex: 0
Repo default GITHUB_TOKEN permission is read, so adding labels would 403 permissions: contents: read, issues: write

The trigger (issues: opened) is unchanged.

Testing

You can't test this from a PR, because issues workflows run only from the default branch. After merging, open a test issue whose body contains e.g. "crash" and check that it gets the bug label. By default the action matches only the issue body. Add include-title: 1 if titles should count too.

🤖 Generated with Claude Code

- github/issue-labeler has no floating v3 tag (only v3.0-v3.5), so @V3
  failed to resolve and the job died during setup. Pin to v3.5.
- enable-versioned-regex is a required input; set it to 0.
- The repo's default GITHUB_TOKEN is read-only; grant issues: write so
  the action can add labels.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Pnwcomputers
Pnwcomputers merged commit 6890d30 into main Nov 17, 2026
1 check passed
@Pnwcomputers
Pnwcomputers deleted the fix/auto-label-workflow branch November 17, 2026 19:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant